frontend/app/analyze/loading/page.tsx (1)

104-132: Fix effect cleanup: intervals/timeouts are not cleared on unmount

The cleanup function returned inside runAnalysis is never registered with useEffect, so progressInterval leaks; redirect timeout also isn’t cleared. Capture timer IDs in the effect scope and clear them in the useEffect return.

Minimal changes within this block:

-        const stepInterval = setInterval(() => {
+        stepInterval = setInterval(() => {
           setCurrentStep((prev) => {
             if (prev < steps.length - 1) {
               return prev + 1;
             } else {
               clearInterval(stepInterval);
-              setTimeout(() => {
-                router.push("/analyze/results");
-              }, 2000);
+              redirectTimeout = setTimeout(() => {
+                router.push("/analyze/results");
+              }, 2000);
               return prev;
             }
           });
         }, 2000);

-        const progressInterval = setInterval(() => {
+        progressInterval = setInterval(() => {
           setProgress((prev) => {
             if (prev < 100) {
               return prev + 1;
             }
             return prev;
           });
         }, 100);
-
-        return () => {
-          clearInterval(stepInterval);
-          clearInterval(progressInterval);
-        };

Additions needed outside this range:

// Declare in the outer scope of the useEffect
let stepInterval: ReturnType<typeof setInterval> | null = null;
let progressInterval: ReturnType<typeof setInterval> | null = null;
let redirectTimeout: ReturnType<typeof setTimeout> | null = null;

// And return a proper cleanup from the useEffect:
return () => {
  if (stepInterval) clearInterval(stepInterval);
  if (progressInterval) clearInterval(progressInterval);
  if (redirectTimeout) clearTimeout(redirectTimeout);
};

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

backend/app/modules/scraper/extractor.py (2)

26-26: Critical: headers passed incorrectly to requests.get (being treated as query params).

Pass headers via the named argument; otherwise the custom User-Agent is never sent.

-            res = requests.get(self.url, self.headers, timeout=10)
+            res = requests.get(self.url, headers=self.headers, timeout=10)

---

24-31: SSRF hardening recommended for URL fetches.

If the URL originates from user input, add guards (scheme allowlist http/https, block private IPs/localhost, DNS pinning, redirect limits) to avoid SSRF.

README.md (3)

137-145: Fix list indentation, fenced code language, stray asterisk, and .env spacing

• MD007: remove extra list indentation.
• MD040: specify a language for fenced block.
• Typo: “Setup environment variables:*” should be italic like other sections.
• .env: remove spaces around “=”.
• Spacing: add space in “/frontend directory”.

-Setup environment variables:*
-  - add .env file in `/frontend`directory.
-  - add following environment variable in your .env file.
-```
-NEXT_PUBLIC_API_URL = http://localhost:8000
-
-```
+*Setup environment variables:*
+- add .env file in `/frontend` directory.
+- add the following environment variable in your `.env` file.
+```env
+NEXT_PUBLIC_API_URL=http://localhost:8000
+```

---

142-142: Clarify dev vs prod URL

Consider adding a brief note that http://localhost:8000 is for local development; use your deployed backend’s HTTPS URL in production to avoid mixed content/CORS issues.

---

163-170: Align backend env block with markdownlint and dotenv conventions

• MD007: remove extra list indentation.
• MD040: add language to the fenced block.
• .env: remove spaces around “=” and fix spacing in “/backend directory”.
• Remove stray indentation before closing fence.

-  - add .env file in `/backend`directory.
-  - add following environment variable in your .env file.
-  ```
-GROQ_API_KEY= <groq_api_key>
-PINECONE_API_KEY = <your_pinecone_API_KEY>
-PORT = 8000
-SEARCH_KEY = <your_Google_custom_search_engine_API_key>
-  ```
+- add .env file in `/backend` directory.
+- add the following environment variables in your `.env` file.
+```env
+GROQ_API_KEY=<groq_api_key>
+PINECONE_API_KEY=<your_pinecone_API_KEY>
+PORT=8000
+SEARCH_KEY=<your_Google_custom_search_engine_API_key>
+```

Optional: include a .env.example with these keys and ensure .env is gitignored.

backend/app/modules/scraper/extractor.py (3)

17-22: UA header OK; consider configurability and locale hints.

Make the UA configurable (env/config) and consider adding an Accept-Language to improve extraction on locale-sensitive sites.

         self.headers = {
-            "User-Agent": (
+            "User-Agent": (
                 "Mozilla/5.0 (Windows NT 10.0; Win64; x64)"
                 " AppleWebKit/537.36 "
                 "(KHTML, like Gecko) Chrome/113.0 Safari/537.36"
             )
-        }
+        ,
+            "Accept-Language": "en-US,en;q=0.9",
+        }

---

71-76: Prefer lxml parser when available; normalize text to reduce noise.

html.parser works, but lxml is faster and more robust if installed. Also consider trimming empty lines to reduce boilerplate.

-            soup = BeautifulSoup(doc.summary(), "html.parser")
-            title = doc.title()
-            text = soup.get_text(separator="\n")
+            try:
+                soup = BeautifulSoup(doc.summary(), "lxml")
+            except Exception:
+                soup = BeautifulSoup(doc.summary(), "html.parser")
+            title = doc.title()
+            raw = soup.get_text(separator="\n")
+            text = "\n".join(line.strip() for line in raw.splitlines() if line.strip())

---

92-92: Standardize the failure payload shape for easier client handling.

Consider returning consistent keys even on failure.

-        return {"url": self.url, "text": "", "error": "Failed to extract article."}
+        return {
+            "url": self.url,
+            "title": "",
+            "text": "",
+            "authors": [],
+            "publish_date": None,
+            "error": "Failed to extract article.",
+        }

backend/app/db/vector_store.py (1)

27-27: Formatting change is fine; consider making provider/region configurable

Single-line spec is OK. For multi-region/multi-cloud deployments, consider sourcing cloud/region from env (e.g., PINECONE_CLOUD, PINECONE_REGION) with sane defaults.

backend/app/modules/vector_store/chunk_rag_data.py (1)

48-53: Avoid recreating fact_fields on every loop; add a type check for fact

• Defining fact_fields inside the loop recreates the list for every iteration; hoist it once above the loop.
• Add a clear type check to avoid TypeErrors when fact isn’t a dict.

Define once above the loop:

fact_fields = ["original_claim", "verdict", "explanation", "source_link"]
for i, fact in enumerate(data["facts"]):
    if not isinstance(fact, dict):
        raise ValueError(f"Fact at index {i} must be a dict")
    for field in fact_fields:
        if field not in fact:
            raise ValueError(f"Missing required fact field: {field} in fact index {i}")

Within this hunk, remove the per-iteration assignment and add the type check:

-            fact_fields = ["original_claim", "verdict", "explanation", "source_link"]
-            for field in fact_fields:
+            if not isinstance(fact, dict):
+                raise ValueError(f"Fact at index {i} must be a dict")
+            for field in fact_fields:
                 if field not in fact:
                     raise ValueError(
                         f"Missing required fact field: {field} in fact index {i}"
                     )

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro